Method and apparatus for guided configuration of unconfigured network and internetwork devices

ABSTRACT

Computer-implemented method and apparatus and associated for constructing a network configuration map comprised of at least two interconnected network entities selected from a series of network entities. A series of configuration scripts, each corresponding to one of the series of network entities include a first section comprised of a first portion containing an icon file for generating an icon representative of the corresponding one of the series of network entities, a second portion containing a set of connection rules for the corresponding one of the series of network entities and a second section containing a series of executable instructions for constructing a configuration file for the network entity. A first software module constructs the network configuration map by generating a workspace, placing first and second icons on the workspace in response to a first input received from a user interface and connecting the icons if the set of connection rules contained in the second portion of the corresponding configuration scripts permit connection therebetween. A second software module then executes the series of instructions contained in the second section of the configuration script to construct a configuration file, suitable for upload to the network device to enable configuration thereof, for a selected one of the connected icons.

A portion of the disclosure of this patent document contains materialwhich is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure, as it appears in the Patent and TrademarkOffice patent file or records, but otherwise reserves all copyrightrights whatsoever.

CROSS REFERENCE TO RELATED APPLICATION

This application is related to co-pending U.S. patent application Ser.No. 08/603,062, filed on even date herewith, entitled "CONFIGURATIONMANAGER FOR NETWORK DEVICES AND AN ASSOCIATED METHOD FOR PROVIDINGCONFIGURATION INFORMATION THERETO", assigned to the Assignee of thepresent application and hereby incorporated by reference as ifreproduced in its entirety.

BACKGROUND OF THE INVENTION

1. Field of the Invention

This application generally relates to computer networks andinternetworks and, more particularly, to a software tool whichconfigures devices to be included in a computer network or internetwork.

2. Description of Related Art

Generally speaking, a network is a collection of user devices, generallyclassified as data terminal equipment (or "DTE"), interconnected forbi-directional exchanges of information. For example, visual displays,computer systems and office workstations are all electronic devicesclassified as DTEs. A local area network (or "LAN") is aninterconnection of plural computer systems distributed around a singlesite. A wide area network (or "WAN") is an interconnection of pluralcomputer systems located at different sites. Traditionally, computersystems have used modems to connect to a WAN via the public switchedtelephone network (or "PSTN") or public switched data network (or"PSDN"). In recent years, WANs which utilize integrated services digitalnetworks (or "ISDNs"), which enable data to be transmitted withoutmodems, to interconnect computer systems have become more common.Finally, an internetwork is a collection of networks interconnected by aWAN.

Devices are initially unconfigured when delivered by the factory.Configuration is a process during which the hardware and software of anunconfigured device is organized and interconnected so that theconfigured device will be able to perform the tasks desired thereof. Asis well appreciated in the art, the wide variety of devices which may beinstalled on a network, as well as the variety of networks which may beconnected to form an internetwork, makes the configuration of networksand internetworks a difficult task which requires highly detailedtechnical knowledge of the various networks, the protocols used to linkwith the various networks and the devices to be installed thereon. Thus,configuration of network devices is often one of the most daunting tasksfacing a network administrator, particularly for those in charge ofsmall and medium size networks have between 100 and 1,000 nodes. Whilesuch networks are relatively complex, their administrators often haveonly minimal training in internetworking administration and may beunfamiliar with routing technology and/or WAN technology.

For example, data link protocols are used to control access to networks.A LAN typically uses the logical link control (or "LLC") subclass of thehigh-level data link control (or "HDLC") protocol as its data linkprotocol. However, an X.25-type packet-switching WAN uses link accessprocedure, balanced (or "LAPB"), a protocol based on HDLC, as its datalink protocol. The data link protocol for an ISDN-type WAN, on the otherhand, may either be a connection-orientated protocol known as frameswitching or a connectionless protocol known as frame relay.

Thus, it can be readily seen from the foregoing that: it would bedesirable to simplify the task of configuring network devices. It is,therefore, the object of this invention to provide an apparatus andassociated method for guiding a user through the complex task ofconfiguring a network device.

SUMMARY OF THE INVENTION

In one embodiment, the present invention is of an apparatus andassociated method, implemented on a computer system, for constructing aconfiguration file for a network device. The apparatus includes aconfiguration script stored in a memory subsystem of the computer systemand a software module executable by a processor subsystem of thecomputer system. The configuration script contains a series ofexecutable instructions for constructing a configuration file for afirst specified type of network device. By executing the instructionscontained in the configuration script, the software module may constructa configuration file suitable for upload to a network device of thefirst specified type for configuration such that the network device maybe configured using the configuration file constructed by the softwaremodule.

In one aspect of this embodiment of the invention, the configurationscript includes a first section which contains a series of configurationcommands which generate requests for information such that informationreceived by the software module in response to the requests forinformation is used to construct the configuration file. In anotheraspect of this embodiment of the invention, the configuration scriptincludes a second section which contains a set of connection rules forconnecting the first specified type of network device to at least oneother specified type of network device. In a related aspect thereof, thefirst section includes a first portion which corresponds to each of theat least one other specified type of network device specified in theconnection rules contained in the second section of the configurationscript. Each such portion contains a subset of the series ofconfiguration commands contained in the first section of theconfiguration script. Each such subset of configuration commands areexecuted only if the network device for which the configuration file isbeing constructed is connected to a network device of the otherspecified type of network device.

In another aspect thereof, the configuration script further includes athird section which defines a backplane bitmap for the network device.In a related aspect thereof, the third section of the configurationscript further includes first, second and third portions. The firstportion defines a bitmap file for generating the backplane bitmap, thesecond portion provides locational information for connected interfaceson the backplane bitmap and the third portion defines an overlay bitmapfor the backplane bitmap for each of the at least one other specifiedtype of network device specified in the connection rules contained inthe second section of the configuration script. In another relatedaspect thereof, the configuration script further includes a fourthsection which contains a user selectable set of commands for each of theconnected interfaces.

In another embodiment, the present invention is of an apparatus andassociated method, implemented on a computer system, for constructing anetwork configuration map comprised of at least two interconnectednetwork entities selected from a series of network entities. Theapparatus includes a series of configuration scripts, each correspondingto one of the series of network entities, stored in the memory subsystemand a first software module, executable by the processor subsystem. Eachone of the series of configuration scripts includes a first sectioncomprised of first and second portions. The first portion contains anicon file for generating an icon representative of the corresponding oneof the series of network entities while the second portion contains aset of connection rules for the corresponding one of the series ofnetwork entities. The software module constructs the networkconfiguration map by generating a workspace, placing at least two iconson the workspace in response to a first input received from a userinterface and connecting first and second ones of the icons placed onthe workspace in response to a second input received from the userinterface if the set of connection rules contained in the second portionof the configuration scripts corresponding to first and second networkentities represented by the first and second icons permit connection ofthe first and second network entities.

In one aspect of this embodiment of the invention, at least one of theseries of configuration scripts further includes a second section whichcontains a series of executable instructions for constructing aconfiguration file for the network entity. In this aspect, the apparatusfurther comprises a second software module, executable by the processorsubsystem in response to a third input received from the user interfacewhich selects an icon previously placed on the network configuration mapfor configuration, for constructing a configuration file if theconfiguration script corresponding to the selected icon is one of theconfiguration scripts having the second section. The configuration fileis constructed by executing the series of instructions contained in thesecond section of the configuration script and appending the constructedconfiguration file to the selected icon. In a further aspect thereof,the series of instructions contained in the second section of theconfiguration scripts includes a series of configuration commands whichgenerate requests for information such that information received by thesecond software module in response to the requests for information isused to construct the configuration file.

In another aspect thereof, the second section of the configurationscripts further include a first portion corresponding to each one of theseries of network entities specified in the set of connection rulescontained in the first portion of the first section of the configurationscript. This portion contains a subset of the series of configurationcommands which are executed only if the network entity for which theconfiguration file is being constructed is connected to a network entityspecified in the set of connection rules. In yet another aspect thereof,the first section of the configuration scripts further include a thirdportion which contains a name for the corresponding one of the series ofnetwork entities. During construction of the network configuration map,the first software module places the name on the network configurationmap if the icon corresponding to the configuration script is placed onthe map.

BRIEF DESCRIPTION OF THE DRAWING

The present invention may be better understood, and its numerousobjects, features and advantages will become apparent to those skilledin the art by reference to the accompanying drawing, in which:

FIG. 1A is a simplified block diagram of a computer system on which anetwork device configuration tool may be installed;

FIG. 1B is a block diagram of a network device configuration toolconstructed in accordance with the teachings of the present invention;

FIG. 2A is a block diagram of a configuration scripts portion of thenetwork device configuration tool of FIG. 1;

FIG. 2B is an expanded block diagram of an attributes section of aconfiguration script of FIG. 2A;

FIG. 2C is an expanded block diagram of a bitmap section of aconfiguration script of FIG. 2A;

FIG. 2D is an expanded block diagram of a bitmap menu section of aconfiguration script of FIG. 2A;

FIG. 2E is an expanded block diagram of a guided configuration sectionof a configuration script of FIG. 2A;

FIG. 3A is a flow chart of a method for guiding configuration of anetwork device in accordance with the teachings of the presentinvention;

FIG. 3B is a flow chart of a map edit portion of the flow chart of FIG.3A;

FIGS. 3C and 3D are a flow chart of a method for determining whether apair of network devices are connectable;

FIG. 4 illustrates a configuration manager GUI for constructing a map ofconfigured network devices with a preconstructed network configurationmap in a network workspace portion thereof;

FIG. 5 illustrates an exemplary guided configuration GUI forconstructing a configuration script for a network device;

FIG. 6 illustrates a backplane bitmap for a configured network device;

FIG. 7 illustrates the configuration manager GUI of FIG. 4 with thepreconstructed network configuration map modified to include newly addedand configured devices therein;

FIG. 8 is a flowchart of a method of configuring a remote network devicein accordance with another aspect of the present invention; and

FIG. 9 illustrates a pop-up bootP GUI in which an unconfigured networkdevice is requesting configuration information.

DETAILED DESCRIPTION

Referring first to FIG. 1A, a computer system 2 suitable for installinga network device configuration tool thereon may now be seen. Thecomputer system 2 is comprised of a processor subsystem 4, for example,a type P6 Pentium processor manufactured by Intel Corporation of SantaClara, Calif., coupled to a memory subsystem 6, for example, a harddrive or other auxiliary memory device capable of storing large amountsof data infrequently used by the processor subsystem 4, by a system bus8, preferably, a 32-bit wide peripheral connection interface (or "PCI")bus. Also coupled to the system bus 8 is a user interface 9. Commonly,the user interface is comprised of three peripheral devices--a videodisplay, a keyboard and a pointing device.

Referring now to FIG. 1B, a network device configuration tool 10constructed in accordance with the teachings of the present inventionwill now be described in greater detail. The network deviceconfiguration tool 10 is graphical user interface (or "GUI") basedsoftware launchable from a suitable platform installed on the computersystem 2. For example, Windows 95 and Windows NT 3.51, both manufacturedby Microsoft of Redmond, Wash., are suitable platforms from which thenetwork device configuration tool 10 may be launched.

In its broadest sense, the network device configuration tool 10 providesa GUI in which the so-called "drag and drop" process is used toconstruct a network configuration map comprised of a series ofinterconnected network devices and/or network entities, for example, aLAN, WAN or other network, from a combination of user inputs, networkconfiguration maps, configuration scripts and local configuration files.

In constructing the network configuration map, a series of localconfiguration files are constructed for the network devices and appendedto the network configuration map. The local configuration files containinformation, for example, internet protocol (or "IP") address, defaultgateway, router name and simplified network management protocol (or"SNMP") community strings, necessary for the network device, forexample, a router, to properly communicate on the network.

For each network device for which a local configuration file has beenconstructed, the network device configuration tool 10 may also constructa network device configuration file suitable for export to the networkdevice itself. In this manner, remote configuration of network devicesis enabled.

As shown in FIG. 1B, the network device configuration tool 10 may berepresentatively illustrated as being comprised of two software modules,map editor 14 and configuration guide 18, both of which are executableby the processor subsystem 4, which retrieve data and programminginstructions from various locations within the memory subsystem 8 of thecomputer system 2 on which the network device configuration tool 10 isinstalled.

The data and programming instruction are stored in the memory subsystem6 as a series of files which may be selectively accessed by the mapeditor 14 and/or the configuration guide 18. Files which are accessibleto the map editor 14 and/or the configuration guide 18 are configurationscripts 12, map files 16, local configuration files 20 and networkconfiguration files 22. The configuration scripts 12 identify the typesof network devices and network entities which may be placed on thenetwork configuration map and interconnected with other network entitiesand network devices. The configuration scripts 12 also identify thenetwork devices which are configurable by the network deviceconfiguration tool 10 and contain information necessary to constructconfiguration files for those network devices. If a particular networkdevice does not have a configuration script, a configuration file cannotbe constructed by the network device configuration tool 10. The mapfiles 16 contain a series of network configuration maps, each comprisedof a series of interconnected network devices and network entities,constructed using the network device configuration tool 10. The localconfiguration files 20 contain information which, if uploaded to thecorresponding network device 26, would enable configuration of thatdevice. If local configuration files 20 are constructed for the networkdevices illustrated on the network configuration map(s) 16 producedusing the network device configuration tool 10, such local configurationfiles 20 are associated with the corresponding network device such thatthey may be directly accessed from the network configuration maps 16.

The network configuration files 22 are similar in content to the localconfiguration files 20 except that the files have been formatted forupload to a network device 26 coupled to the configuration tool in amanner to be more fully described below. Broadly speaking, a localconfiguration file 20 is modified for upload to the correspondingnetwork device 26 by formatting the local file into the appropriate IPaddress for the target network device 26. Finally, the network deviceconfiguration tool 10 includes a reverse parser 24 coupled to the localconfiguration files 20 and the network configuration files 22. Thereverse parser 24 is used to construct a local configuration file 20from a network configuration file 22 downloaded to the networkconfiguration tool 10 by the network device 26.

It is contemplated that the network device configuration tool 10 wouldbe installed in the computer system 2 operated by a networkadministrator and that plural network devices 26 and other networkentities, only one of which is shown in FIG. 1B for ease ofillustration, would be coupled to the network device configuration tool10. Utilizing the network device configuration tool 10, the networkadministrator may build a representative network configuration map forthe network. The network administrator may then configure remotelylocated network devices by uploading configuration files constructedduring the process of building the network configuration map to thedevices. Thus, by using the network configuration tool, the networkadministrator can, from a central location, design a suitableconfiguration network and then configure any number of remotely locateddevices included in the network.

The network device configuration tool 10 is coupled to the networkdevice 26 by an asynchronous interface 28 and a boot protocol (or"bootp")/trivial file transfer protocol (or "TFTP") manager 30. Underthe control of an asynchronous manager (not shown), a software processwithin the processor subsystem 4, the asynchronous interface 28 is usedto exchange configuration information, for example, a networkconfiguration file 20, by either an in-band transfer via in-bandconnection 29a, for example, via telnet, or by an out-of-band transfervia out-of-band connection 29b, for example, via modem. Additionally,the bootp/TFTP manager 30, another software process within the processorsubsystem 4, controls the exchange of bootp and TFTP messages betweenthe network device configuration tool 10 and the network device 26.Generally, a bootp exchange is used to transfer raw address and otherbasic information so that a TFTP exchange may then be used to transferconfiguration information. The bootp/TFTP manager 30 also controlsaccesses to bootptab files 32.

As will be more fully described with respect to FIG. 3, below, theconfiguration scripts 12 are used to direct map editor 14 andconfiguration guide 18 in a guided configuration of a selected networkdevice 26 by guiding in the construction of a configuration file for thedevice. Accordingly, turning momentarily to FIG. 2A, the configurationscripts 12 used to guide the configuration of a selected network device26 will now be described in greater detail. As may now be seen, theconfiguration scripts 12 are comprised of a series of separate scripts12-1 through 12-N, one for each type of device which may configured bythe configuration tool 12. Each script 12-1 through 12-N is comprised ofan attributes section 34, a bitmap section 36, a bitmap menu section 38and a guided configuration section 40. Each of these sections 34, 36, 38and 40 is a selectively executable set of commands which may be usedduring configuration of a device of the type corresponding to aparticular script 12-1 through 12-N.

Turning now to FIG. 2B, the attributes section 34 is comprised of anicon portion 34a, a network entity portion 34b, a description portion34c and a series of connection portions 34d-1 through 34d-N. A validicon filename identifying the graphical icon to be associated with thedevice type corresponding to the configuration script 12-N is containedin the icon portion 34a. As will be more fully described below, thisicon will appear in a device window of a configuration GUI and can bedragged onto a network workspace to add a device of that type to anetwork configuration map. The network entity portion 34b provides aunique name for the type of device and appears in the device windowunder the icon. The description portion 34c defines a defaultdescription for the device which pre-populates the dialog box when adevice type is dragged onto the network workspace. Finally, theconnection portions 34d-1 though 34d-N provides connection statementsfor the device type. Specifically, a connection portion 34d will beprovided for port, modular slot or other type of connection interfacefor the device type. Each connection statement will include a physicalname for the port or other type of connection interface and the networkentity names for all other types of devices which may be connected tothe port. For example, if the network device was a modular router having4 PCI slots, each connectable to ethernet, X.25, frame relay, PPP andIDSN type entities, and an ethernet port connectable to an ethernetentity, the attributes section 34 could be as set forth in the followingcode:

    ______________________________________                                        :ATTRIBUTES                                                                   ICON ROUTER.ICO                                                               NETENTITY "Compaq Router"                                                     DESCRIPTION "Modular and Fast"                                                ______________________________________                                        CONNECT "PCI SLOT 1"                                                                         "Ethernet" "X.25"                                                                           "Frame Relay"                                                   "PPP" "ISDN"                                                   CONNECT "PCI SLOT 2"                                                                         "Ethernet" "X.25"                                                                           "Frame Relay"                                                   "PPP" "ISDN"                                                   CONNECT "PCI SLOT 3"                                                                         "Ethernet" "X.25"                                                                           "Frame Relay"                                                   "PPP" "ISDN"                                                   CONNECT "PCI SLOT 4"                                                                         "Ethernet" "X.25"                                                                           "Frame Relay"                                                   "PPP" "ISDN"                                                   CONNECT "Ethernet Port"                                                                      "Ethernet"                                                     ______________________________________                                          ©1995 Compaq Computer Corporation                               

Turning next to FIG. 2C, the bitmap section 36 defines the "drill down"bitmap which is presented to the network administrator upon requestingsubsequent configuration of a configured network device. The bitmapsection 36 also defines any necessary overlay bitmaps as well asprovides the locations of "hot spots" on the bitmap. The bitmap is agraphical representation of the backplane of the configured device whichprovides connection information for the ports thereof. "Hot spots" onthe bitmap are paths to additional information related to the connectedports for the configured network device.

Bitmap file portion 36a names a valid window bitmap format file whichwill be displayed in its own window when the network administratordouble clicks on a configured network device. For each connected port ofthe configured network device, the bitmap section 36 will also include alocation port portion 36b-1 through 36b-N which provides the location ofthe hot spot for the connected port on the bitmap. Finally, the bitmapsection includes an overlay device bitmap file 36c-1 through 36c-x foreach type of network device or entity which is connectable to theconfigured network device. Then, if the configured device is connectedto that particular network entity, the network entity can be representedon the bitmap.

For example, if the bitmap 36 is comprised of a bitmap file 36a, portlocations 36b-1 and 36b-2 and overlay device file 36c-1 as set forth inthe sample code below:

    ______________________________________                                               BITMAP "router.bmp"                                                           LOCATE "Slot 1" 20 40                                                         LOCATE "Port 1" 50 90 70 120                                                  OVERLAY "Ethernet" "TLAN.BMP"                                          ______________________________________                                          ©1995 Compaq Computer Corporation                               

The bitmap 36 will include a representation of an ethernet-type networkentity stored at TLAN.BMP drawn on top of the representation of abackplane of a router stored at ROUTER.BMP at coordinates 20, 40 if the"Ethernet"-type network entity is plugged into "Slot 1".

The bitmap menu section 38 defines a menu hierarchy presented to theuser for hot spots, for example, connected slots, on the bitmap and theexecutable commands for each item included in a command menu. Thecommand menu is displayed when the network administrator clicks on aconnected slot on the bitmap. The bitmap menu section 38 is subdividedinto network entity command sections 38a-1 through 38a-x. Specifically,for each network entity for which connection to the device is allowed, acorresponding network entity command section is provided such that, ifthat network entity is connected to the device, the commands defined inthe section will be displayed to the network administrator for selectiveexecution thereof.

The guided configuration section 40 defines the GUIs used to guide auser through configuration of a device and controls the configurationfile to be constructed using user responses to the GUIs. As illustratedin FIG. 2D, the guided configuration section 40 is subdivided into ageneral script command portion 40a and a port script command portion40b-1 through 40b-N for each port to which the device is connectable. Aguided configuration script for a Cisco 2514 router is set forth inAppendix A by way of example and will be described in greater detailwith respect to FIGS. 3-D, below.

Returning now to FIG. 1B, the network device configuration tool 10 willnow be described in greater detail. Generally, the map editor 14controls the generation of a map of a network configuration whiledelegating the task of configuring unconfigured devices placed on thenetwork configuration map to the configuration guide 18. Upon initiationof the configuration process, the map editor 14 selectively retrieves amap file 16, or creates a blank map, for editing. To add a device of aselected type to the network configuration map, the map editor 14retrieves the corresponding configuration script 12-N from theconfiguration scripts 12 and, using the information contained in theretrieved configuration script 12-N, places an unconfigured device ofthe selected type on the network configuration map and appends a namefor the device to the map. The map editor 14 performs all operations inwhich editing of the network configuration map is proposed. For example,if a connection between two devices placed on the network configurationmap is proposed, the map editor 14 reviews the configuration scripts 12for the devices and, if a connection between the two devices ispermitted, the map editor 14 completes the proposed connection andappends the connection information to the network configuration map.

If a request to configure a device placed on the network configurationmap is received, the map editor 14 transfers the name and connectioninformation for the device to the configuration guide 18 and instructsthe configuration guide 18 to perform the requested configuration task.For example, if configuration of a network device is requested, theconfiguration guide 18 will retrieve the configuration script 12-N forthat type of network device and execute the instructions contained inthe guided configuration section 40 thereof. Using the informationprovided by the configuration script 12, the map editor 14 and inputprovided by the network administrator in response to execution of theinstructions contained in the guided configuration section 40, theconfiguration guide 18 builds a local configuration file, associatedwith the device, for use by the network administrator and acorresponding network configuration file suitable for upload to thenetwork device to enable configuration of the network device.

Referring next to FIG. 3A, the method for guiding configuration of anetwork device by constructing a configuration file for the networkdevice which is the subject of the present invention shall now bedescribed in greater detail. It should be clearly understood, however,that the illustrated order of steps is purely exemplary and should notbe construed as limiting the scope of the invention. The methodcommences at step 42 by launching the network device configuration tool10 from a platform such as Windows '95 by selecting an icon previouslydesignated as providing a path to the network device configuration tool10.

Proceeding to step 44, once launched, the network device configurationtool 10 generates a configuration manager GUI 100 (see FIG. 4) whichprovides a network workspace 102 and a device window 104. In the networkworkspace 102, a map comprised of any number of interconnected networkdevices, each having a configuration tied thereto, may be produced. Thedevice window 104, on the other hand, displays all of the types ofnetwork devices which may be placed on the network workspace 102.Continuing on to step 46, for each type of network device for which aconfiguration script 12-N has been prepared and stored in the memorysubsystem 6, the network device configuration tool 10 places an iconrepresentative of the network device type in the device type window 104to indicate to the user which types of network devices are configurableby the network device configuration tool 10. For example, the devicewindow 104 illustrated in FIG. 4 includes icons representative of a PPPlink, a vendor specific modular router, an ISDN-type WAN, anEthernet-type LAN, a non-vendor specific computer subsystem, anX.25-type packet-switching WAN, and an ISDN-type WAN which subscribes toframe relay-mode service. At step 48, the network device configurationtool 10 loads a blank map into the network workspace 102. At this stage,the network device configuration tool 10 has completed loading theconfiguration manager GUI 100 and is ready to execute selected commandsin response to inputs received from the network administrator via theuser interface 9.

Proceeding on to step 50, the network administrator selects a command,either from one of the pull-down menus listed on the pull-down menu bar108 or by depressing a command button displayed on command button bar110. The menus displayed on the pull-down menu bar 108 are "file","edit", "network", "window" and "help". By selecting one of these menus,a series of commands, each of which relates to the selected menu, aredisplayed. Available file commands are "new", "open", "save", "save as","print", "print setup" and "exit". The new command clears the networkworkspace 102 of any network configuration map placed thereon. The opencommand allows the network administrator to select a networkconfiguration map to be placed on the network workspace 102. The saveand save as commands stores the map placed on the network workspace 102to the memory subsystem 6. The print command prints the networkconfiguration map placed on network workspace 102. The print setupcommand displays the printer configuration for the computer system 10.The exit command closes the network configuration tool.

Commands available under the edit menu are "draw mode", "move mode","workspace properties", "edit device", "view/configure device", "deletedevice", "all ports connected configuration", "update configuration","retrieve configuration", "associate configuration", "telnet to thisdevice". The draw mode command allows the network administrator to drawconnections between devices displayed on the network workspace 102. Theworkspace properties command is, in fact, a second pull-down menu whichallows the network administrator to tailor the map placed in the networkworkspace 102. Commands available under the workspace properties menuare "view entity name", "view entity description", "view entityconnections", "view ip addresses", "view ipx addresses", all of whichadd the listed information to the display of each device on the map, andthe "snap to grid" and "view grid", both of which orientate the map to agrid.

The edit device command accesses the configuration informationassociated with a selected network device. The view/configure commanddisplays a view of the backplane of a selected configured network deviceor, if the selected network device is unconfigured, defaults to theconfiguration dialog set forth in greater detail below. The deletedevice command removes a selected network device or entity from thenetwork workspace. The all ports configured, update configurationprovides access to a selected device's configuration file. The retrieveconfiguration file allows the network administrator to directly access aconfiguration file stored in the memory subsystem 6 while the associateconfiguration command permits the network administrator to append aconfiguration file to a device. The telnet to the device commandinitiates an in-band transfer of configuration information from thenetwork device configuration tool 10 to the network device 26.

Commands available under the network menu are "bootptab maintenance","enable bootp server", "disable bootp server", "enable TFTP server","disable TFTP server" and "view network activity log". All of thesecommands are relate to the exchange of configuration information betweenthe network device configuration tool 10 and the network device 26. Morespecifically, the bootptab maintenance command enables the networkadministrator to review previously constructed bootptab files 32. Theenable/disable bootp server commands control the operation of thecomputer system 2 on which the network device configuration tool 10operates as a bootp server, i.e. is capable of sending and/or receivingbootp messages via the bootp/TFTP manager 30. When enabled as a bootpserver, the computer system 2 listens for bootp requests placed on thenetwork by devices requesting configuration information. Theenable/disable TFTP server commands control operation of the computersystem 2 on which the network device configuration tool 10 operates as aTFTP server, i.e. is capable of sending and/or receiving TFTP messagesvia the bootp/TFTP interface 30. Finally, the view network activity logprovides a historical display of exchanges between the network deviceconfiguration tool 10 and network devices requesting configuration.

Commands under the window menu are "arrange", "configuration files""workspace", "requesting router" and "network devices". The arrangecommand is a pull-down menu which provides a set of commands whichmodify the appearance of the configuration management GUI 100. Theconfiguration files command displays the configuration files stored inthe memory subsystem. The workspace and network device commandsrespectively move the network administrator to the network workspace 102and the device window 104. Finally, the requesting router commandprovides a list of network devices 26 requesting IP addresses andconfiguration files from the network device configuration tool 10.

The command button bar 110 provides immediate execution of selectedcommands available from the pull-down menus 108. The commands which maybe executed from the command button bar 110 are new, open, save, print,draw mode, move mode, network devices, workspace, requesting router,view network activity log and help.

Proceeding to step 52, the network administrator executes the commandselected at step 50. For example, if the network administrator decidesto retrieve an existing network configuration map stored in memory, thenetwork administrator may click on the "open map" command button on thecommand button bar to display a list of map files 16 stored in memoryand then select a map file to be opened. An exemplary networkconfiguration map 106 which may be stored in memory is illustrated inFIG. 4. The network configuration map 106 is comprised of a vendorspecific device 112, here, a modular router manufactured by CompaqComputer Corporation of Houston, Tex., having a first peripheralconnection interface (or "PCI") slot coupled to a first ethernet-typeLAN 114, a second PCI slot coupled to a second ethernet-type LAN 116, athird PCI slot coupled to a frame relay-type WAN 118 and an ethernetport coupled to a third ethernet-type LAN 120.

Continuing on to step 54, the network administrator then decides whetherto edit the network configuration map 106 displayed in the networkworkspace 102. If the network administrator decides not to edit thenetwork configuration map 106, the method proceeds to step 56 where thenetwork administrator decides whether to execute another command. If so,the method returns to step 56. Otherwise, the network administratorcloses the network configuration tool at step 58 to end the method.

Returning now to step 54, if the network administrator decides to go tothe network workspace 102 to edit either the blank map initially loadedinto the network workspace 102 at step 48 or, if a saved map wasretrieved from the map files 16 by executing an "open file" command atstep 52, the retrieved map loaded into the network workspace at step 52,the method proceeds to step 59 (FIG. 3B) where the network administratordecides whether to edit the map displayed in the network workspace 102.If the network administrator decides not to edit the map, the methodreturns to step 56 (FIG. 3A). If, however, the network administratordecides to edit the configuration network map 106 displayed in thenetwork workspace 102 the method proceeds to step 60 where editing ofthe map commences.

At step 60, the network administrator may select a device type displayedin device type window 104 and add a device of the selected type to themap 106 displayed in network workspace 102. Proceeding to step 62, toadd a device of a type displayed in the device type window 104 to thenetwork configuration map 106, displayed in the network workspace 102,the user selects an icon representing a desired device type and, usingthe "drag and drop" process, places the icon on the networkconfiguration map 106 displayed in the network workspace 102. Forexample, using a mouse or other conventional pointing device, the userwould point to an icon representing the desired device type, select thedevice type by holding a leftmost button on the mouse in the depressedposition, point to the desired position on the map and release thebutton. By doing so, a new device of the selected type is added to thenetwork map. For example, in FIG. 7, a single network device, i.e., amodular router 122 manufacture by Compaq Computer Corporation, and apair of network entities, i.e., ethernet type LANs 124 and 126 have beenadded to the network configuration map 106.

Each network device and/or network entity added to the networkconfiguration map 106 is associated with a corresponding one of theconfiguration scripts 12-N. Accordingly, at step 64, the map editor 14displays the name of the network device or entity contained in theattributes section 34 of the corresponding configuration script 12-N asthe name of the newly added network device or entity. For example, thename of the network device 122 added to the network configuration map106 is "Compaq Router".

Upon placing the, as yet unconnected, network device 122 and entities124, 126 on the network configuration map 106, or if it was decided atstep 60 to not add a network device or entity to the networkconfiguration map 106, the method proceeds to step 66 where the networkadministrator decides whether to connect the newly added network devicesand entities 122, 124 and 126 to other network devices or entities. Forexample, the network administrator may decide to connect the Compaqrouter 122 to the frame relay-type WAN 118, the ethernet-type LAN 124and the ethernet-type LAN 126. If the network administrator decides toconnect the Compaq router 122 to the ethernet-type LAN 124, the methodproceeds to step 68 where the network administrator would select theCompaq router 122 by holding a leftmost button on the mouse in thedepressed position while pointing to the Compaq router 122, draw aconnection between the Compaq router 122 and the ethernet-type LAN 124by repositioning the mouse to point at the ethernet-type LAN 124 whilethe button is depressed and releasing the button to complete theconnection.

Continuing on to step 70, the map editor 14 determines whether theproposed connection is permissible. If the proposed connection ispermitted, the line drawn by the network administrator is completed atstep 72. The connection interface(s) for the origination device are thenplaced on the network configuration map 106 and the method continues onto step 74 for further editing of the network configuration map 106. Forexample, as shown in FIG. 7, PCI slot 1 of the Compaq router 122 hasbeen used to connect the device to the ethernet-type LAN 126, PCI slot 2to connect to the frame relay-type WAN 118 and PCI slot 4 to connect tothe ethernet-type LAN 124. If, however, the proposed connection is notpermitted, the line drawn by the user is deleted at step 76 beforecontinuing on to step 74.

Returning to step 70, the method by which the map editor 14 determineswhether the proposed connection is permitted will now be described ingreater detail. An initial determination as to whether the proposedconnection is permissible is made based upon the contents of theattributes section 34 of the configuration scripts 12-N for the devicesplaced on the map 106. For example, the configuration script for a Cisco2514 router is set forth in the attached appendix. A portion of theattributes section of the configuration script contains the followingcode:

    ______________________________________                                        CONNECT "ETHERNET0" "Ethernet"                                                CONNECT "ETHERNET1" "Ethernet"                                                CONNECT "SERIAL0"   "X.25" "Frame Relay" "PPP" "HDLC"                         CONNECT "SERIAL1"   "X.25" "Frame Relay" "PPP" "HDLC"                         ______________________________________                                          ©1995 Compaq Computer Corporation                               

This portion of the configuration script code contains considerableconnection information for the device. Specifically, the device has fourconnection interfaces--two ethernet ports and two serial ports.Furthermore, the two ethernet ports are only connectable to anethernet-type LAN entities device while the two serial ports areconnectable only to X.25, frame relay, PPP and HDLC entities.Accordingly, at step 70, the mapper compares the list of network deviceor entity types which are connectable for the two devices and/orentities for which connection is proposed. If the devices and/orentities are connectable, the method proceeds to step 72 whereconnection of the two devices and/or continues.

Turning momentarily to FIG. 3D, the step of connecting the two devicesand/or entities will now be described in greater detail. The methodcommences at step 150 and continues on to step 152 where theconfiguration file for the origination device or entity is reviewed todetermine if the origination device or entity has an available slotwhich is connectable to the destination device or entity and to step 154where the configuration file for the destination device or entity isreviewed to determine if the destination device or entity has anavailable slot which is connectable to the origination device or entity.If either the origination or destination device or entity do not have anavailable slot which is connectable to the other device or entity, adetermination is made at step 156 that the devices/entities cannot beconnected. The proposed connection is then deleted at step 158 and,continuing on to step 166, the method returns to step 72.

Returning to step 154, if it is determined that both the origination anddestination devices or entities have available slots, the methodproceeds to step 160 where a connection interface is selected for theoriginating device and on to step 162 where a connection interface isselected for the destination device or entity. At both of these steps,the network administrator may select any one of a list of availableconnection interfaces overlayed on the network configuration map 106 bythe network device configuration tool 10. If only one connectioninterface is available for a device or entity, however, the map willautomatically select the available interface and indicate its selectionof the connection interface to the network administrator. Upon selectingconnection interfaces for the devices or entities, the method proceedsto step 164 where the selected connection interface for the device 122is displayed on the network configuration map 106 and on to step 166 fora return to step 72.

Upon either a decision not to connect devices or entities at step 66, acompletion of a proposed connection at step 72 or a deletion of aproposed connection at step 76, the method proceeds to step 74 where thenetwork administrator decides whether to configure a device. To initiateconfiguration of a selected unconfigured device, the networkadministrator double clicks on the device to be configured. At step 78(FIG. 3C) the configuration guide 18 retrieves the guided configurationsection 40 from the configuration script 12-N for the type of device tobe configured and, proceeding to step 80, executes the script commandscontained in the general script commands portion 40a of the guidedconfiguration section 40. In turn, the execution of the script commandscauses a series of questions to be asked of the network administrator,the answers to which are used to construct a configuration file. Forexample, if the script commands set forth in the guided configurationsection of the configuration script set forth in Appendix A wereexecuted during configuration of a Cisco 2514 router, the networkadministrator would be asked to name the router, indicate whether toconfigure internet protocol (or "IP") for the router, indicate which IProuting protocol should be used for the router, whether to configure IPXfor the router, indicate whether the router should be passwordprotected, choose a password for the router, indicate whether theconfiguration mode for the router should be password protected andchoose a password for the configuration mode.

Proceeding to step 82, the configuration guide 18 determines whether anyports of the device being configured are connected to a second device orentity. If any of the ports are connected, the method proceeds to step84 where the configuration guide 18 executes the script commands for theconnected ports. For example, if serial port 1 of a Cisco router 2514was connected to a WAN, the configuration guide 18 would execute thescript commands set forth in seriall portion of the script commands setforth in Appendix A. Thus, in this example, the network administratorwould be asked whether the serial port should be configured, the IPaddress and mask for the port, the IPX network number, whether the portshould be configured for frame relay, the type of connector being usedfor the port, the local data link connection identifier (or "DLCI"), theCommitted Information Rate (or "CIR") and the Excess Information Rate(or "EIR") for the port and whether to use compression.

The configuration guide 18 collects the information necessary toconfigure the device by engaging the network administrator in a dialogduring which the configuration guide 18 generates a series of GUIs, eachof which displays a request for information and provides areas in whichthe requested information may be inputted and buttons for guiding thenetwork administrator through the dialogue. By way of example, an IPaddress GUI 200 is illustrated in FIG. 5. The network administrator mayinput the IP address and mask for the indicated slot and device byrespectively entering the IP address and mask in areas 202 and 204. Thenetwork administrator may also review a prior GUI in the dialogue bydepressing button 206, proceed to the next GUI in the dialogue bydepressing button 208, request help by depressing button 210 or exit theconfiguration dialog by depressing button 212.

Upon successful execution of the script commands for the connected portsat step 84, or if it was determined at step 82 that no ports areconnected for the device being configured, the configuration dialog iscompleted at step 86 and, at step 88, the information provided by thenetwork administrator during the dialogue is used to construct a localconfiguration file 20 for the device. If desired, the networkadministrator may view the local configuration file 20 constructedduring this process at step 90, directly edit any of the configurationcommands contained therein at step 92 before saving the constructedlocal configuration file 20 to the memory subsystem and associating itwith the device. Selected portions of the configuration informationcontained in the local configuration file 20 may be displayed on thenetwork configuration map 106. For example, FIG. 7 displays the IPaddress and mask for PCI slot 1 of the Compaq router 122 which was inputby the network administrator during configuration of the device. Thenetwork configuration map 106 may also include a indicator 128, forexample, a loop surrounding a device, which indicates that a device hasbeen configured.

Having successfully constructed a local configuration file 20 andassociated it with the device being configured, the method proceeds tostep 96 (FIG. 3B) where the network administrator decides whether toupload the configuration file to the device. If upload is selected, themethod proceeds to step 97 where the constructed configuration file isuploaded to the network device 26. Various mechanisms may be used toupload a constructed configuration file to the network device 26. Forexample, in many circumstances, an in-band transfer of the configurationfile via telnet may be used. In other circumstances, other mechanismsmore fully described below may be necessary to transfer configurationinformation to the network device 26.

While constructing a local configuration file for a device, the networkdevice configuration tool 10 also constructs a bootptab file for thedevice. The bootptab file is particularly useful in those situationswhere the network administrator decides not to upload the configurationfile upon completing the construction thereof, for example, if thenetwork device is unconnected, powered down or otherwise unavailable. Abootptab file for a device contains the serial number for the device tobe configured, an IP address to assign to the device to be configuredand the configuration file to be uploaded to the device. As will be morefully described with respect to FIGS. 8-9, below, the bootptab fileprovides information necessary for unattended remote configuration ofnetwork devices as they are connected to the network.

Returning now to FIG. 3B, after completing upload of the configurationfile at step 97, or if the network administrator decided at step 96 notto upload the configuration file, the method proceeds to step 98 wherethe network administrator decides whether to perform subsequentconfiguration on a device on the network configuration map 106. Ifsubsequent configuration of a device is selected, the method proceeds tostep 99 where subsequent configuration of a selected device is performedfrom a backplane bitmap of the selected device. To select a device forsubsequent configuration, the network administrator double clicks on aconfigured device included on the network configuration map 106. Bydoing so, a bitmap of the backplane of the selected configured device isdisplayed.

FIG. 6 illustrates a backplane bitmap 220 for the Compaq router 122 ofFIG. 7. As may now be seen, the various connection interfaces used toconnect the router 122 to network entities, as well as unconnectedconnection interfaces, are graphically displayed on the backplane bitmap220 using the information contained in the bitmap section 36 of theconfiguration script 12-N and the local configuration file 20 for theCompaq router 122. Specifically, for the Compaq router 122, PCI slot 1has been used to provide a first ethernet connection 222, PCI slot 2, anHSSI connection 224 and PCI slot 4, a second ethernet 226. PCI slot 3,however, remains unconnected. From the backplane bitmap 220, the networkadministrator may view the settings for a port by double clicking on aselected port or, by depressing the right mouse button, bring up a pulldown menu of commands contained in the network entity commands section38a-x of the bitmap menu 38 for the network entity connected to theselected port and select any of the configuration commands listed on thepull down menu for execution.

After completing subsequent configuration of the device at step 99, orif the network administrator decided at step 98 not to performsubsequent configuration, the method returns to step 56 (FIG. 3A).

Turning next to FIG. 8, a method of transmitting configurationinformation to a network device 26 in accordance with the teachings ofthe present invention shall now be described in greater detail. Themethod commences at step 250 by launching the network deviceconfiguration tool 10. As previously stated with respect to FIG. 3A,launch of the network device configuration tool 10 initiates thegeneration of the configuration manager GUI 100. In addition, launch ofthe network device configuration tool 10 initiates listening, by thenetwork device configuration tool 10 at step 252, for the presence ofunconfigured network devices 26 on the network.

Proceeding to step 254, the network device configuration tool 10 willdetect bootp packets transmitted on the network and determine if thebootp packet was issued by a device requesting configuration informationfrom the network device configuration tool 10. More specifically, if anunconfigured network device 26 powers up on the network, theunconfigured network device 26 will periodically issue a bootp packetwhich contains a medium access code (or "MAC") address for the deviceand a code which indicates that the device is requesting configurationinformation. For example, the code may be placed in the vendor specificfield of the bootp packet. If a detected bootp packet does not contain arequest for configuration information, the method returns to step 252where the configuration tool continues to listen for bootp packets.

If, however, the network device configuration tool 10 determines at step256 that the issuing device is requesting configuration information, forexample, by matching a request code held by the network deviceconfiguration tool 10 with a corresponding code contained in thedetected bootp packet, the method proceeds to step 258 where the networkdevice configuration tool 10 will determine if the device requestingconfiguration information has a corresponding bootptab file 32 and ifthe description of the device requesting configuration informationmatches the device drawn on the network configuration map 106.

In order to determine whether the device requesting configurationinformation has a corresponding bootptab file 32 and if the descriptionof the device matches the device drawn on the network configuration map,the attributes section 34 must be modified to include two additionalportions--bootpid and subdeviceid. The bootpid portion contains a numberunique to a particular device type and model number. The subdeviceididentifies the type of devices installed in the device. For example, ifthe network device was a modular router having 4 PCI slots, eachconnectable to ethernet, X.25, frame relay, PPP and IDSN type entities,and an ethernet port connectable to an ethernet entity with a ThunderLanboard connectable to ethernet entities, a W-Adapter connectable to X.25,frame relay and PPP entities and a Basic Rate ISDN Board connectable toISDN entities installed therein, the attributes section 34 could be asset forth in the following code:

    ______________________________________                                        :ATTRIBUTES                                                                   ICON ROUTER.ICO                                                               NETENTITY "Compaq Router"                                                     DESCRIPTION "Modular and Fast"                                                ______________________________________                                        CONNECT "PCI SLOT 1"                                                                         "Ethernet" "X.25"                                                                           "Frame Relay"                                                   "PPP" "ISDN"                                                   CONNECT "PCI SLOT 2"                                                                         "Ethernet" "X.25"                                                                           "Frame Relay"                                                   "PPP" "ISDN"                                                   CONNECT "PCI SLOT 3"                                                                         "Ethernet" "X.25"                                                                           "Frame Relay"                                                   "PPP" "ISDN"                                                   CONNECT "PCI SLOT 4"                                                                         "Ethernet" "X.25"                                                                           "Frame Relay"                                                   "PPP" "ISDN"                                                   CONNECT "Ethernet Port"                                                                      "Ethernet"                                                     ______________________________________                                         bootpid 103                                                                   subdeviceid 11 "ThunderLan board" "Ethernet                                   subdeviceid 12 "WAdapter" "X.25" *2 "Frame Relay" *2 "PPP" *2                 subdeviceid 13 "Basic Rate ISDN Board" "ISDN                                   ©1995 Compaq Computer Corporation                               

The guided configuration section would be similarly modified to includean additional command script portion which, upon execution thereof, willissue any additional requests for information, for example, installeddevices, necessary to construct the bootptab file described herein suchthat a determination as to whether the description of the devicerequesting configuration matches the device drawn on the networkconfiguration map 106.

Proceeding to step 260, if the device requesting configuration has amatching bootptab file, i.e., the bootptab file has a bootpid whichmatches the serial number of a device having a bootptab file and if thedevices installed in the device requesting configuration match thedevices identified in the subdeviceid portion of the configuration filefor the matching bootptab file, the network device configuration tool 10issues a bootp reply at step 260. The bootp reply contains the filenamewhich matches the configuration file described in the matching bootptabfile. Using the filename contained in the bootp reply, at step 262, thedevice requesting configuration may issue a TFTP request forconfiguration information to the network device configuration tool 10which identifies the configuration file containing its configurationinformation.

Continuing on to step 264, in response to the TFTP request containingthe filename of a configuration file issued by the device requestingconfiguration, the network device configuration tool 10 responds byissuing the requested configuration file to the device. At step 266, theunconfigured network device configures itself using the informationcontained in the configuration file transmitted thereto by the networkdevice configuration tool 10 and, at step 268, the method ends.

Returning to step 258, if the device requesting configuration does nothave a matching bootptab file, the method proceeds to step 270 where thenetwork device configuration tool 10 generates a pop-up requestingdevice GUI 300 which overlays a portion of the configuration manager GUI100. A requesting device GUI 300 is illustrated in FIG. 9. Asillustrated herein, the requesting device GUI 300 includes an iconrepresenting the unconfigured network device 302 requestingconfiguration.

Proceeding to step 272, the network administrator may select one of twooptions to configure the device requesting configuration. If the networkadministrator decides that the device 302 is a new device, therequesting device may be dropped onto the network workspace 102, therebyadding the requesting device to the network configuration map 106 as anunconnected device. Proceeding on to step 274, the method would returnto step 64 (FIG. 3B) wherein the previously discussed process ofconstructing a configuration file and uploading the configuration fileto the unconfigured network device may be completed to configure thedevice requesting configuration.

Returning to step 272 and, now proceeding to step 276, the networkadministrator may instead opt to drop the device 302 requestingconfiguration onto an existing device, for example, router 112, alreadyincluded on the network configuration map 106. By dropping the device302 requesting configuration onto an existing device on the networkconfiguration map 106, the network administrator is indicating that thedevice 302 requesting configuration is the same device that is alreadyon the network configuration map 106 but, due to a difference betweenthe description of the device 302 in the bootptab and the description ofthe device 112 contained in the corresponding configuration file, thenetwork device configuration tool 10 is unable to recognize that the twoare the same device.

Proceeding on to step 278, the network device configuration tool 10would reconcile the configuration file and the bootptab file for thedevice. If the two are irreconcilable, the method terminates at step280. If the two can be reconciled, the configuration file is revisedappropriately at step 282 and the method then returns to step 264 sothat the network device configuration tool 10 may issue the revisedconfiguration file to the device 302 requesting configuration in themanner previously described. To reconcile the device 302 requestingconfiguration and an existing device such as the router 112, the networkdevice configuration tool 10 reviews the devices installed on the devicerequesting configuration match the devices installed. If the installeddevices match, then the configuration file is modified using thecontents of the bootptab file. The method then proceeds to step 264 sothat the network device configuration tool 10 may issue the revisedconfiguration file to the device 302 requesting configuration.

Thus, there has been described and illustrated herein an apparatus andassociated method for constructing a configuration file for a networkdevice suitable for upload to the network device to enable theconfigurement thereof. However, those skilled in the art will recognizethat many modifications and variations besides those specificallymentioned may be made in the techniques described herein withoutdeparting substantially from the concept of the present invention.Accordingly, it should be clearly understood that the form of theinvention described herein is exemplary only and is not intended as alimitation on the scope of the invention. ##SPC1##

What is claimed is:
 1. For a computer system having a processorsubsystem and a memory subsystem coupled by a system bus forbi-directional exchanges therebetween, an apparatus for constructing aconfiguration file for a network device, comprising:at least oneconfiguration script stored in said memory subsystem, said configurationscript being executed to construct a configuration file for a firstspecified type of network device, said configuration script includes afirst section containing a series of configuration commands whichgenerate requests for information; and a second section containing a setof connection rules for connecting said first specified type of networkdevice to at least one other specified type of network device, for eachconnection interface, said connection rules are selected from aplurality of connection rules corresponding to each network device; anda software module, executable by said processor subsystem, forconstructing a configuration file suitable for upload to a networkdevice of said first specified type by executing said configurationscript, wherein information received by said software module in responseto said requests for information is used to construct said configurationfiles, and wherein said network device is configurable using saidconfiguration file constructed by said software module.
 2. An apparatusfor constructing a configuration file for a network device according toclaim 1 and wherein said first section of said configuration scriptfurther comprises:a first portion corresponding to each of said at leastone other specified type of network device specified in said connectionrules contained in said second section of said configuration script;said first portion containing a subset of said series of configurationcommands which are executed only if said network device for which saidconfiguration file is being constructed is connected to a network deviceof said other specified type of network device.
 3. An apparatus forconstructing a configuration file for a network device according toclaim 2 and wherein said configuration script further comprises:a thirdsection which defines a backplane bitmap for said network device.
 4. Anapparatus for constructing a configuration file for a network deviceaccording to claim 3 and wherein said third section of saidconfiguration script further comprises:a first portion which defines abitmap file for generating said backplane bitmap; a second portion whichprovides locations, on said backplane bitmap, of connected interfaces;and a third portion which defines at least one overlay bitmap for saidbackplane bitmap; wherein said third portion includes an overlay bitmapfor each of said at least one other specified type of network devicespecified in said connection rules contained in said second section ofsaid configuration script.
 5. An apparatus for constructing aconfiguration file for a network device according to claim 4 whereinsaid configuration script further comprises:a fourth section whichcontains a user selectable set of commands for each of said connectedinterfaces.
 6. An apparatus for constructing a configuration file for anetwork device according to claim 1, wherein said second section of saidconfiguration script comprises:an identifier for each connectioninterface of said first specified type of network device; and a list ofnetwork device types that can be connected to the connection interfaceassociated therewith, said list being provided for each of saididentifiers.
 7. For a computer system having a system bus and aprocessor subsystem, a memory subsystem and a user interfacerespectively coupled to said system bus for bi-directional exchangestherebetween, an apparatus for constructing a network configuration mapcomprised of at least two interconnected network entities selected froma series of network entities, said apparatus comprising:a series ofconfiguration scripts stored in said memory subsystem, each one of saidseries of configuration scripts corresponding to one of said series ofnetwork entities, and each one of said series of configuration scriptsincluding a first section comprised of first and second portions; saidfirst portion of each one of said series of configuration scriptscontaining an icon file for generating an icon representative of saidcorresponding one of said series of network entities; and said secondportion of each one of said series of configuration scripts containing aset of connection rules for said corresponding one of said series ofnetwork entities, for each connection, said connection rules areselected from a plurality of connection rules corresponding to eachnetwork entity; and a first software module, executable by saidprocessor subsystem, for constructing a network configuration map bygenerating a workspace, placing at least two icons on said workspace inresponse to a first input received from said user interface andconnecting first and second ones of said at least two icons placed onsaid workspace in response to a second input received from said userinterface if said set of connection rules contained in said secondportion of said first section of said configuration scriptscorresponding to first and second network entities represented by saidfirst and second icons permit connection of said first and secondnetwork entities.
 8. An apparatus for constructing a networkconfiguration map according to claim 7 wherein at least one of saidseries of configuration scripts further comprises:a second section; saidsecond section of said at least one of said series of configurationscripts including a series of executable instructions for constructing aconfiguration file for said network entity; said apparatus furthercomprising: a second software module, executable by said processorsubsystem in response to a third user input selecting an icon placed onsaid map for configuration, for constructing a configuration file ifsaid configuration script corresponding to said selected icon is one ofsaid at least one configuration script having said second section byexecuting said series of instructions contained in said second sectionof said configuration script and appending said constructedconfiguration file to said selected icon.
 9. An apparatus forconstructing a network configuration map according to claim 8 andwherein said series of instructions contained in each one of said atleast one configuration scripts having said second section furthercomprises:a series of configuration commands which generate requests forinformation; wherein information received by said second software modulein response to said requests for information is used to construct saidconfiguration file.
 10. An apparatus for constructing a networkconfiguration map according to claim 9 wherein said second section ofeach one of said at least one configuration scripts having said secondsection further comprises:a first portion corresponding to each one ofsaid series of network entities specified in said set of connectionrules contained in said first portion of said first section of saidconfiguration script; said first portion of said second sectioncontaining a subset of said series of configuration commands which areexecuted only if said network entity for which said configuration fileis being constructed is connected to a network entity specified in saidset of connection rules contained in said first portion of said firstsection of said configuration script.
 11. An apparatus for constructinga network configuration map according to claim 10 wherein said firstsection of each one of said series of configuration scripts furthercomprises:a third portion which contains a name for said correspondingone of said series of network entities; said first software moduleplacing said name on said map if said icon corresponding to saidconfiguration script is placed on said map.
 12. A method forconstructing a configuration file for a network device, saidconfiguration file suitable for upload to said network device to enableconfiguration thereof, said method comprising the steps of:providing aconfiguration script containing a series of executable instructions forconstructing a configuration file for a first specified type of networkdevice, said configuration script including a first section having aseries of configuration commands and a second section containing a setof configuration rules for connecting said first specified type ofnetwork device to at least one other specified type of network device,for each connection interface, said connection rules are selected from aplurality of connection rules corresponding to each network device;generating request for information by executing said series ofconfiguration commands contained in said first section of saidconfiguration script; and constructing said configuration file using atleast information received in response to said request for informationgenerated by executing said series of configuration commands containedin said first section of said configuration script.
 13. A method forconstructing a configuration file for a network device according toclaim 12 wherein the step of providing a configuration script containinga series of executable instructions further comprises the stepof:providing a configuration script which includes a first portioncorresponding to each of said at least one other specified type ofnetwork device specified in said connection rules contained in saidsecond section of said configuration script; each said first portioncontaining a subset of said series of configuration commands.
 14. Amethod for constructing a configuration file for a network deviceaccording to claim 13 and further comprising the step of:executing saidsubset of said series of configuration commands contained in each saidfirst portion only if said network device for which said configurationfile is being constructed is connected to a network device of said otherspecified type of network device.
 15. A method for constructing aconfiguration file for a network device according to claim 12, whereinsaid second section of said configuration script comprises:an identifierfor each connection interface of said first specified type of networkdevice; and a list of network device types that can be connected to theconnection interface associated therewith, said list being provided foreach of said identifiers.
 16. A method for constructing a networkconfiguration map comprised of at least two interconnected networkentities selected from a series of network entities, comprising thesteps of:providing a series of configuration scripts, each of whichcorresponds to one of said series of network entities and includes afirst section comprised of first and second portions;said first portionof each one of said series of configuration scripts containing an iconfile for generating an icon representative of said corresponding one ofsaid series of network entities; and said second portion of each one ofsaid series of configuration scripts containing a set of connectionrules for said corresponding one of said series of network entities, foreach connection, said connection rules are selected from a plurality ofconnection rules corresponding to each network entity; generating afirst icon representative of a first one of said network entities;generating a second icon representative of a second one of said networkentities; and connecting said first and second icons if said set ofconnection rules contained in said second portion of said first sectionof said configuration scripts corresponding to first and second networkentities represented by said first and second icons permit connection ofsaid first and second network entities.
 17. A method for constructing anetwork configuration map according to claim 16 wherein the step ofproviding a series of configuration scripts further comprises the stepof:providing at least one configuration script which includes a secondsection having a series of executable instructions for constructing aconfiguration file for said network entity.
 18. A method forconstructing a network configuration map according to claim 17 andfurther comprising the step of:selecting an icon placed on said map forconfiguration; constructing a configuration file for said network devicerepresented by said icon if said configuration script for said networkdevice represented by said selected icon is said configuration scripthaving said second section; executing said series of instructionscontained in said second section of said configuration script for saidnetwork device represented by said selected icon; and appending saidconstructed configuration file to said selected icon.
 19. For a computersystem having a processor subsystem and a memory subsystem coupled by asystem bus for bi-directional exchanges therebetween, an apparatus forconstructing a configuration file for a network device, comprising:aplurality of configuration scripts for various different types ofnetwork devices, said configuration scripts being stored in said memorysubsystem, and each of the configuration scripts including at least oneconfiguration script stored in said memory subsystem, said configurationscript being executed to construct a configuration file for a firstspecified type of network device, said configuration script includes afirst section containing a series of configuration commands whichgenerate requests for information; and a second section containing a setof connection rules for connecting said first specified type of networkdevice to at least one other specified type of network device, for eachconnection interface, said connection rules are selected from aplurality of connection rules corresponding to each network device; andfirst computer program code for enabling selection of a particular oneof the various different types of network devices; and second computerprogram code for executing the one of said configuration scriptsassociated with the particular one of the various different types ofnetwork devices to produce a configuration file for the particular oneof the various different type of network devices.
 20. An apparatus forconstructing a configuration files for network devices according toclaim 19, wherein each of the configuration scripts further includes aseries of commands, andwherein the series of commands associated with aparticular one of said configuration scripts are executed by said secondcomputer program when said second computer program code executes theparticular one of said configuration scripts.
 21. An apparatus forconstructing a configuration files for network devices according toclaim 20,wherein dialog screens for the user to input information areproduced when said second computer program code executes the one of saidconfiguration scripts associated with the particular one of the variousdifferent types of network devices, and wherein said second computerprogram code prompts the user to enter the input information, and usedthe input information that the user enters in producing theconfiguration file.
 22. An apparatus for constructing a configurationfiles for network devices according to claim 19, wherein said apparatusfurther comprises:third computer program code for uploading theconfiguration file to a network device of the particular one of thevarious different types of network devices.
 23. An apparatus forconstructing a configuration files for network devices according toclaim 19, wherein the executing of the one of said configuration scriptsby said second computer program code prompts a user of said apparatus toenter information, and the entered information is used by said secondcomputer program code in producing the configuration file.
 24. Anapparatus for constructing a configuration files for a network devicesaccording to claim 19, wherein the connection rules includes anidentifier for the associated port and a list of network devices thatare permitted to connect to the associated port.